Mutex Lock/Lock Profiler

Lock profiling enables you to understand the lock contention and blocking thread behavior of your applications over time. It helps you identify method calls in the context within which most locks for resources were allocated and combine this information with the number of allocated objects.

  1. Go to Configurations > Actions > Lock Profiler, the Lock Profiler window is displayed.
Figure 118: Lock Profiler

2. Click the Add New Session button , and the Topology Details window is displayed.

Figure 119: Topology Details Window

3. Navigate to the instance via the Topology tree and click the Mutex Lock The Mutex Lock Profiling Session Configuration window is displayed.

Figure 120: Mutex lock Profiling Session Configuration Window

4.Provide the following configuration details:

General

  • Session Name: Name of the mutex lock profiling session.
  • Duration: Total duration of the session in minutes. Default – 30 minutes, Minimum – 5 minutes, and Maximum – 120 minutes.
  • Session Overhead: Number of sessions to be executed per minute. Low (10 sessions/minute), Medium (20 sessions/minute), or High (30 sessions/minute). You can also choose any intermediary values (sessions/minute).
  • of Top Mutex Lock to capture: Number of top mutex locks to be captured
  • Description: Description of the mutex locks.

Advanced

  • Top N Mutex Lock Find Duration: Time of pass 1 from the total duration (% of total session time) in seconds. Default – 30%, Minimum – 10%, Maximum – 50%.
  • Total No. Mutex Lock to capture: Total number of mutex locks to analyze. Default – 20, Minimum – 5, Maximum – 1000.
  • Total No. of threads to capture: Total number of threads to analyze for mutex locks. Default – 100, Minimum – 10, Maximum – 1000.
  • Total No. of stack trace to capture: Total stack trace during the session. Default – 1000, Minimum – 100, Maximum – 10000.

5. After the configuration, when you click the Start button, a new session of Mutex Lock starts. You can view all the sessions in the Mutex Lock profiling window.

Note:

  • When any mutex session is started, a running icon is displayed, which denotes the session is running for Mutex lock.
  • You can delete a session by clicking the button. 
Figure 121

6. This window displays the following details:

  • Top Blocking Locks
  • Top Blocked Threads
  • Top Blocking Threads

Top Blocking Locks

Class Data

Figure 122: Class Data (Top Blocking Locks)

Statistics

Figure 123: Statistics (Top Blocking Locks)

Top Blocked Threads

Class Data

Figure 124: Class Data (Top Blocked Threads)

Statistics

Figure 125: Statistics (Top Blocked Threads)

Top Blocking Threads

Thread Data

Figure 126: Thread Data (Top Blocking Thread)

Statistics

Figure 127: Statistics (Top Blocking Thread) 
Previous
Next